Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

2135

reference
69-tree-1
name
2135
tree-preservation-order

undefined

69-tpo-1
uprn
address-text
point
POINT (-1.035283 50.891800)
geometry
MULTIPOLYGON (((-1.035227 50.891794,-1.035229 50.891805,-1.035237 50.891815,-1.035250 50.891823,-1.035265 50.891828,-1.035283 50.891830,-1.035300 50.891828,-1.035316 50.891823,-1.035329 50.891816,-1.035337 50.891806,-1.035340 50.891794,-1.035338 50.891783,-1.035330 50.891773,-1.035318 50.891765,-1.035302 50.891760,-1.035284 50.891758,-1.035267 50.891760,-1.035251 50.891765,-1.035238 50.891772,-1.035230 50.891782,-1.035227 50.891794)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL